-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed broken Julia LSP support + fixed broken MarkDown LSP support #1101
base: main
Are you sure you want to change the base?
Conversation
…o have the same in `is_installed_args`. Otherwise, it is erroneously brought to believe that Julia Language Server is not installed.
…ed-language-server` was not found. Now, it is possible to specify multiple locations with `script` were to look for the node script.
… Relative directories such as `.` as was before configured are no longer supported.
…wn-languageserver`
…wn-languageserver`
…35eaf67c34f37e87b52a10f43cfd
@@ -213,17 +213,18 @@ class LanguageServerManagerAPI(LoggingConfigurable, HasListeners): | |||
help=_("additional absolute paths to seek node_modules first"), | |||
).tag(config=True) | |||
|
|||
def find_node_module(self, *path_frag): | |||
def find_node_module(self, node_module, alternatives): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this constitutes a breaking change as language specs inheriting from NodeModuleSpec
will no longer work. One way to add it in backward compatible way would be to add a new method with new signature and make the old method call the new one.
Thank you for the PR, sorry I missed it back in October! |
References
unified-language-server
withvscode_markdown_languageserver
. See issues raised at https://discourse.jupyter.org/t/how-to-install-and-run-markdown-language-server/24286/3Code changes
Changes are documented in the commits.
User-facing changes
No visual changes in the settings.
Backwards-incompatible changes
No changes to API.
Chores
I am glad to contribute to all chores if the PR will be considered and the bugs eventually fixed upstream. Before investing more time, I prefer to wait for some reactions from the maintainers. Thanks for your understanding.
Changes are anyhow very limited and small in their extent.